Summary

• model aqua github_artifact_attestations.predicate_type
• pass predicate filters into GitHub attestation detection and verification for aqua packages
• bypass the digest-only versions-host attestation cache when a predicate filter is configured

Field References

• aqua github_artifact_attestations docs: https://aquaproj.github.io/docs/reference/registry-config/github-artifact-attestations/
• aqua Go config type for predicate_type: https://pkg.go.dev/github.com/aquaproj/aqua/v2/pkg/config/registry#GitHubArtifactAttestations
• GitHub REST attestation predicate_type query filter: https://docs.github.com/en/rest/orgs/attestations?apiVersion=2022-11-28#list-attestations
• GitHub CLI gh attestation verify --predicate-type: https://cli.github.com/manual/gh_attestation_verify
• SPDX specification index: https://spdx.dev/specifications/

Packages Using This Field

Current aqua-registry entries using github_artifact_attestations.predicate_type:

• foundry-rs/foundry: https://github.com/aquaproj/aqua-registry/blob/main/pkgs/foundry-rs/foundry/registry.yaml#L41-L43
  • configured predicate: https://spdx.dev/Document/v2.3
  • Foundry generates an SPDX SBOM with Syft and then creates an SBOM attestation for the release archive: https://github.com/foundry-rs/foundry/blob/master/.github/workflows/release.yml#L291-L345
• gleam-lang/gleam: https://github.com/aquaproj/aqua-registry/blob/main/pkgs/gleam-lang/gleam/registry.yaml#L143-L145 and https://github.com/aquaproj/aqua-registry/blob/main/pkgs/gleam-lang/gleam/registry.yaml#L162-L164
  • configured predicate: https://spdx.dev/Document/v2.3
  • Gleam generates SPDX and CycloneDX build SBOMs, then attests the release archive using the SPDX SBOM path: https://github.com/gleam-lang/gleam/blob/main/.github/actions/build-release/action.yml#L215-L270

SPDX SBOM vs SLSA Provenance

SPDX is a standard Software Bill of Materials format. An SPDX SBOM answers "what is in this artifact?" It lists package/component metadata such as dependencies, versions, relationships, licenses, and related identifiers. The predicate value https://spdx.dev/Document/v2.3 identifies an in-toto/GitHub attestation whose predicate payload is an SPDX 2.3 document.

SLSA provenance answers "where and how did this artifact come from?" It describes the source, builder, workflow, build inputs, and build parameters for an artifact. The common GitHub provenance predicate is https://slsa.dev/provenance/v1.

Short version: SPDX SBOM is inventory; SLSA provenance is build origin.

Why Foundry and Gleam Use SPDX Here

Both package entries point at release workflows that generate SBOMs and create GitHub artifact attestations with an SBOM payload. That means the attestation the registry is asking aqua/mise to verify is specifically an SPDX SBOM attestation, not the default SLSA provenance attestation.

This does not mean SLSA is unimportant or unavailable. It means this particular aqua registry field is being used to select the SBOM attestation for the release archive. Foundry also has a separate generic/provenance-style attestation step, but the aqua registry entry explicitly configures the SPDX predicate for the archive SBOM attestation.

Why aqua Supports This

GitHub artifact attestations are not limited to SLSA provenance. GitHub's API and gh attestation verify both accept a predicate type filter so callers can select provenance, SBOM, release, or custom predicate attestations. aqua exposes predicate_type so registry entries can preserve that upstream verification policy instead of hard-coding one attestation kind.

Why mise Needs This

mise consumes aqua-registry metadata. If mise ignores predicate_type, it cannot faithfully implement the registry's requested verification policy for packages like Foundry and Gleam.

Before this PR, predicate_type was not parsed or sent to GitHub. For these packages, mise treated GitHub artifact attestation verification as "find any valid attestation for this artifact and signer workflow." That could pass by verifying a different predicate type when multiple attestations exist, or pass an SPDX attestation only accidentally because the unfiltered API result happened to include it. It did not enforce "verify the SPDX SBOM attestation" as requested by aqua-registry.

This PR changes that behavior by sending predicate_type to GitHub during detection and verification. Because mise's versions-host attestation cache is keyed by digest only, predicate-filtered requests bypass that cache and query GitHub directly.

Tests

• mise run format (includes cargo check --all-features)
• cargo test -p aqua-registry test_github_artifact_attestations_predicate_type -- --nocapture
• cargo test -p mise-sigstore attestations_url_includes_predicate_type -- --nocapture
• git diff --check

Summary by CodeRabbit

• New Features

  • GitHub artifact attestations now support an optional predicate-type filter sourced from registry metadata and applied during provenance detection and cryptographic verification, and attestation fetches include predicate-type when present.

• Tests

  • Added unit tests covering predicate-type deserialization, URL construction including predicate-type, and predicate-filtered attestation behavior.